Friendlier HTML form controls with a little CSS magic. Designed for IE9+, as well as the latest Chrome, Safari, and Firefox.
Created by @mdo.
<label class="control checkbox">
<input type="checkbox">
<span class="control-indicator"></span>
Check this custom checkbox
</label>
<label class="control radio">
<input id="radio1" name="radio" type="radio">
<span class="control-indicator"></span>
Toggle this custom radio
</label>
<label class="control radio">
<input id="radio2" name="radio" type="radio">
<span class="control-indicator"></span>
Or toggle this other custom radio
</label>
Each checkbox and radio is wrapped in a <label>
for three reasons:
<input>
s.<input>
automatically, meaning no JavaScript is required.We hide the default <input>
with opacity
and instead use the <span class="control-indicator">
within the <label>
to build a new custom form control.
With the sibling selector (~
), we use the :checked
state to trigger a makeshift checked state on the custom control.
In the checked states, we use base64 embedded SVG icons from Open Iconic. This provides us the best control for styling and positioning across browsers and devices.
By default, checkboxes use a checkmark and radios use an filled circle. Also included are two modifier classes, .control-x
and .control-dash
, to change things up should the need arise.
Add the modifier classes to the <label>
, like so:
<label class="control checkbox control-x">...</label>
Want to customize the icons further, or use other ones? Download Open Iconic—included are font files, PNGs, and SVGs.
<div class="select">
<select aria-label="Select menu example">
<option selected>Open this select menu</option>
<option value="1">One</option>
<option value="2">Two</option>
<option value="3">Three</option>
</select>
</div>
We wrap the <select>
in a <div>
as a wrapper that we can generate custom styles on with CSS's generated content.
Previously, we used a <label>
as the wrapper, but this can result in unintended behavior with assistive technologies. For instance, some screen readers will end up reading all <option>
s contained in the <select>
as one long label for the form control. To still provide label text for assistive technologies, we instead use an appropriate aria-label
attribute.
The <select>
has quite a few styles to override and includes a few hacks to get things done. Here's what's happening:
appearance
is reset to none
for nearly all styles to correctly apply across modern browsers (meaning not IE9).:-moz-focusring
is overridden so that on focus there's no inner border in Firefox.Heads up! This one comes with some quirks right now:
option
s looks rather ugly.color
.select[multiple]
elements is basically impossible because <option>
s are presently unstylable in all browsers.Any ideas on improving these are most welcome.
<label class="file">
<input type="file" id="file" aria-label="File browser example">
<span class="file-custom"></span>
</label>
The file input is the most gnarly of the bunch. Here's how it works:
<input>
in a <label>
so the custom control properly triggers the file browser.<input>
via opacity
.:after
to generate a custom background and directive (Choose file...).:before
to generate and position the Browse button.height
on the <input>
for proper spacing for surrounding content.aria-label
attribute.In other words, it's an entirely custom element, all generated via CSS.
Heads up! The custom file input is currently unable to update the Choose file... text with the filename. Without JavaScript, this might not be possible to change, but I'm open to ideas.
<progress class="progress" value="25" max="100">
25%
</progress>
<progress class="progress" value="50" max="100">
50%
</progress>
<progress class="progress" value="75" max="100">
75%
</progress>
<progress class="progress" value="100" max="100">
100%
</progress>
The <progress>
element is actually pretty straightforward to style, but it does have some gotchas. Here's the deal:
.progress
.<progress>
element. For example, in WebKit browsers, ::-webkit-progress-bar
is the background bar and ::-webkit-progress-value
is the colored progress bar within.::-webkit-
and ::-moz-
pseudo selectors will nullify your styles. (It's worth noting this happens with other pseudo selectors like placeholder
).<progress>
. The only quirk there is that you must set the color
property on the <progress>
element to colorize the progress bar within.For more information, read the rather thorough CSS Tricks article. There you'll find gotchas around generated content, browser quirks, and more. The MDN also has an informative article on the progress element.
The width
is automatically set by the browser, but you can easily change it by adding some CSS to .progress
.
.progress {
width: 100%;
}
<progress class="progress" value="25" max="100">
<div class="progress">
<span class="progress-bar" style="width: 25%;">
25%
</span>
</div>
</progress>
IE10 natively supports the <progress>
element, but IE9 doesn't. Instead, they simply show as plain text values. However, IE9 support is just a few hacks away:
<progress>
element to simulate the background and inner progress bar.<progress>
behavior, we add text-indent: -999rem;
to the custom .progress-bar
to hide the text value.Once applied, you can use the IE9-compatible snippet in all browsers. However, I encourage you to only do so should you need IE9 support.
For the time being, WTF, forms? is limited to checkboxes, radio buttons, select menus, file inputs, and progress bars. Additional custom inputs will depend on browser support.
for
attributes?We nest our <input>
s and <select>
s within a <label>
, so there's no need to specify a for
attribute as the browser will automatically associate the two.
hover
states?Basic hover styles have been included, but they've been commented out because they are sticky on iOS. Uncomment if you really need it.
Not for the time being, however, the file input might be better off with it.
Possibly, but not until v4 at the earliest.
Initial testing done by @patrick_h_lauke (on version 2.2.0) with various standard combinations (Internet Explorer/Firefox with JAWS15/NVDA on Windows, Safari with VoiceOver on OS X and iOS, Chrome with TalkBack on Android) does not show any adverse effects.
For a full changelog, visit the releases page on GitHub.
This project utilizes SemVer for versioning releases for maximum backward compatibility.